|
|
| Author |
Thread Statistics | Show CCP posts - 0 post(s) |
Tom Bithof
Universal Allies Inc.
4
   |
Posted - 2013.04.24 22:37:00 -
[1] - Quote
Same problem. I've tried the tricks offered elsewhere, including switching to another user and back. I'd rather not download the game a fifth time. Some DEV attention to what is apparently not that rare a problem would be appreciated.
If anyone else is experiencing this problem, posting here might help CCP prioritize it. |
Tom Bithof
Universal Allies Inc.
5
|
Posted - 2013.04.26 02:52:00 -
[2] - Quote
Thanks DoubleTap, that's something I haven't tried. I don't really have a good spot to do that... and I can't play so.. maybe the logs will show something! No, not *those* logs, they never show anything. I mean my Router's outgoing IP logs.
Router's Outgoing Log Table
Columns are: Destination URL/IP and Service/Port Number
with occasional -descriptions of progress and "on screen messages."
--Pressed PS3 button to turn on PS3
74.125.225.129www
74.125.225.130www
198.107.156.1543478
198.107.156.1543479
198.107.156.1553479
23.60.78.34HTTPS
-Selected "User 1" button to sign in as User 1 and automatically connect to the Sony Network
205.185.206.210www
173.230.216.168HTTPS
198.107.131.100HTTPS
184.169.182.184HTTPS
23.60.113.215HTTPS
23.60.113.62www
198.107.157.1445223
184.169.182.184HTTPS
23.60.131.49www
198.107.131.100www
205.185.206.210www
23.60.131.49www
205.185.206.210www
205.185.206.225www
23.60.113.62www
205.185.206.225www
-Launched Dust 514
23.60.113.164HTTPS
87.237.38.220HTTPS
87.237.38.200HTTPS
204.160.124.126www
"You are about to connect to CCP Dust 514 servers. ..."
-Pressed "X - OK" button
173.230.216.145HTTPS
87.237.38.220HTTPS
87.237.39.227HTTPS
87.237.38.200HTTPS
173.230.216.145HTTPS
69.16.175.10www
87.237.39.231HTTPS
"Synchronizing... 12/53
..12%"
"Cached data files corrupt. Please reinstall game. ..."
-Pressed "X - OK" button
8.27.81.254www
"You are about to connect to CCP Dust 514 servers. ..."
-Pressed "X - OK" button
173.230.216.145HTTPS
87.237.38.220HTTPS
87.237.39.227HTTPS
87.237.38.200HTTPS
173.230.216.145HTTPS
69.16.175.10www
87.237.39.231HTTPS
"Synchronizing... 12/53
..12%"
Is everyone's else's Dust 514 synchronizing progress bar stalling in the same place, if not at the same IP? Sometimes I don't get to 12%, sometimes I stall on 1 or 2% progress, but the IP logs look the same.
|
Tom Bithof
Universal Allies Inc.
5
|
Posted - 2013.04.26 02:58:00 -
[3] - Quote
So maybe some of us are timing out on Synchronizing progress, with occassional luck on retries, because the ping to one of the servers on this list is particularly bad. Will Ping/Traceroute show anything useful?
PING 87.237.39.231 ( 87.237.39.231 ) : 56 data bytes
64 bytes from 87.237.39.231: icmp_seq=0, ttl=240 times=120. ms
64 bytes from 87.237.39.231: icmp_seq=1, ttl=240 times=120. ms
64 bytes from 87.237.39.231: icmp_seq=2, ttl=240 times=110. ms
64 bytes from 87.237.39.231: icmp_seq=3, ttl=240 times=120. ms
64 bytes from 87.237.39.231: icmp_seq=4, ttl=240 times=120. ms
--- 87.237.39.231 ping statistics ---
packets transmitted = 5 , packets received = 5 packet loss = 0%
round-trip min/avg/max = 110/118/120
traceroute to 87.237.39.231 (87.237.39.231) ,30 hops max,40 byte packet
...(skipping the entries near my end)...
15 212.187.160.66 (212.187.160.66) 100. 0 ms 100. 0 ms 100. 0 ms
16 87.237.37.246 (87.237.37.246) 120. 0 ms 120. 0 ms 120. 0 ms
17 87.237.39.231 (87.237.39.231) 110. 0 ms 120. 0 ms 120. 0 ms
Traceroute Complete.
120ms seems reasonably quick... working back through the list of IPs I get to:
PING 173.230.216.145 ( 173.230.216.145 ) : 56 data bytes
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
--- 173.230.216.145 ping statistics ---
packets transmitted = 5 , packets received = 0 packet loss = 100%
Maybe I can't ping 173.230.216.145 because its HTTPS port is meant to be a little more secure.
traceroute to 173.230.216.145 (173.230.216.145) ,30 hops max,40 byte packet
...
4 151.164.103.200 (151.164.103.200) <10.0 ms 10. 0 ms <10.0 ms
5 12.122.133.197 (12.122.133.197) 10. 0 ms 10. 0 ms 10. 0 ms
6 12.249.183.6 (12.249.183.6) 10. 0 ms 10. 0 ms 10. 0 ms
7 66.192.250.254 (66.192.250.254) 60. 0 ms 60. 0 ms 60. 0 ms
8 66.209.64.141 (66.209.64.141) 60. 0 ms 60. 0 ms 60. 0 ms
9 66.209.64.122 (66.209.64.122) 60. 0 ms 60. 0 ms 60. 0 ms
10 216.115.64.182 (216.115.64.182) 60. 0 ms 60. 0 ms 60. 0 ms
11 () * * *
12 () * * *
13 () * * *
14 () * * *
15 () * * *
Is any of this useful to the Devs? If the problem is latency related, will their own tests of the client's interactions with the servers simulate sufficient latency to duplicate whatever trouble we (of modest broadband connections) are having? Anyone? Any Devs? ... Bueller? |
|
|
| |
|